Method and system for using idle computing power of an electric vehicle

ABSTRACT

A method for using idle computing power of an electric vehicle includes receiving computing tasks while the electric vehicle is electrically connected to a charging infrastructure, accepting to perform the computing tasks while the electric vehicle is electrically connected to the charging infrastructure, and in response to accepting to perform the computing tasks, performing the computing tasks while the electric vehicle is electrically connected to the charging infrastructure.

INTRODUCTION

The present disclosure relates to a system and method for using idlecomputing power of an electric vehicle.

This introduction generally presents the context of the disclosure. Workof the presently named inventors, to the extent it is described in thisintroduction, as well as aspects of the description that may nototherwise qualify as prior art at the time of filing, are neitherexpressly nor impliedly admitted as prior art against this disclosure.

In certain situations, computing power is needed to perform computingtasks. It is therefore desirable to identify computing devices with idlecomputing power that can perform those computing tasks.

SUMMARY

The present disclosure describes a system and method for using idlecomputing power of an electric vehicle. The presently disclosed methodallows idle computing power in the electric vehicle to be used for otherapplications, such as parallel, distributed, edge, and blockchainapplications. The idle computing power of the electric vehicle may besold, thereby offsetting the cost of owning the electric vehicle.

In an aspect of the present disclosure, the method for using idlecomputing power of an electric vehicle includes receiving computingtasks while the electric vehicle is electrically connected to a charginginfrastructure, accepting to perform the computing tasks while theelectric vehicle is electrically connected to the charginginfrastructure, and in response to accepting to perform the computingtasks, performing the computing tasks while the electric vehicle iselectrically connected to the charging infrastructure. The methoddescribed in this paragraph improves vehicle technology and computertechnology by using idle computing power available in electric vehiclefor other applications, such as parallel, distributed, edge, andblockchain applications.

In an aspect of the present disclosure, the method further includesdetermining a computing capability and capacity of a vehicle controllerof the electric vehicle. Accepting to perform the computing tasks whilethe electric vehicle is electrically connected to the charginginfrastructure includes determining whether the computing capacity ofthe vehicle controller of the electric vehicle is sufficient to performthe computing tasks and accepting to perform the computing tasks whilethe electric vehicle is electrically connected to the charginginfrastructure in response to determining that the computing capacity ofthe vehicle controller of the electric vehicle is sufficient to performthe computing tasks.

In an aspect of the present disclosure, the method further includesreceiving a task rate for performing the computing tasks, receiving acharging rate for charging the electric vehicle, determining a netprofit using the charging rate for charging the electric vehicle and thetask rate for performing the computing tasks, comparing the net profitwith a predetermined profit threshold to determine whether the netprofit is equal to or greater than the predetermined profit threshold,and determining that the net profit is equal to or greater than thepredetermined profit threshold. Accepting to perform the computing taskswhile the electric vehicle is electrically connected to the charginginfrastructure includes accepting to perform the computing tasks whilethe electric vehicle is electrically connected to the charginginfrastructure in response to: (a) determining that the computingcapacity of the vehicle controller of the electric vehicle is sufficientto perform the computing tasks and (b) determining that the net profitis equal to or greater than the predetermined profit threshold. Themethod further includes performing the computing tasks in response toaccepting to perform the computing tasks.

In an aspect of the present disclosure, the charging infrastructure is aselected charging infrastructure of a plurality of charginginfrastructures. The method further includes searching for the pluralityof charging infrastructures that are located within a predetermineddistance from the electric vehicle, a predetermined place or particularlocation (e.g., city, place), receiving the task rate for performing thecomputing tasks for each of the plurality of charging infrastructuresthat are located within the predetermined distance from the electricvehicle, receiving the charging rate for charging the electric vehiclefor each of the plurality of charging infrastructures that are locatedwithin the predetermined distance from the electric vehicle, anddetermining the net profit for each of the plurality of charginginfrastructures that are located within the predetermined distance fromthe electric vehicle using the task rate for performing the computingtasks for each of the plurality of charging infrastructures that arelocated within the predetermined distance from the electric vehicle andthe charging rate for charging the electric vehicle for each of theplurality of charging infrastructures that are located within thepredetermined distance from the electric vehicle. The method furtherincludes comparing the net profit for each of the plurality of charginginfrastructures that are located within the predetermined distance fromthe electric vehicle with a predetermined profit threshold to determinewhether the net profit is equal to or greater than the predeterminedprofit threshold to determine profitable charging infrastructures. Theprofitable charging infrastructures are the plurality of charginginfrastructures that are located within the predetermined distance fromthe electric vehicle and that would result in the net profit that isequal to or greater than the predetermined profit threshold. The methodfurther includes receiving a selection from a vehicle operator of one ofthe profitable charging infrastructures.

In an aspect of the present disclosure, the method further includeswirelessly receiving the computing tasks from a remote server while thecharging infrastructure is electrically charging the electric vehiclethrough a charge port of the electric vehicle.

In an aspect of the present disclosure, the method further includesreceiving the computing tasks from a remote server through the charginginfrastructure, and the electric vehicle is electrically connected tothe charging infrastructure through a charge port of the electricvehicle.

In an aspect of the present disclosure, the method further includesusing an idle computing power of a vehicle controller of the electricvehicle to perform the computing tasks while the electric vehicle iselectrically connected to the charging infrastructure through a chargeport of the electric vehicle.

In an aspect of the present disclosure, the vehicle controller performsthe tasks at the same time as the charging infrastructure iselectrically charging the electric vehicle.

In an aspect of the present disclosure, the method further includesreceiving a task rate for performing the computing tasks, receiving acharging rate for charging the electric vehicle; determining a netprofit using the charging rate for charging the electric vehicle and thetask rate for performing the computing tasks, comparing the net profitwith a predetermined profit threshold to determine whether the netprofit is less than the predetermined profit threshold, determining thatthe net profit is less than the predetermined profit threshold,declining to perform the computing tasks while the electric vehicle iselectrically connected to the charging infrastructure in response todetermining that the net profit is less than the predetermined profitthreshold, and refraining from performing the computing tasks inresponse to declining to perform the computing tasks.

In an aspect of the present disclosure, the method further includesdetermining a computing capacity of a vehicle controller of the electricvehicle, determining whether the computing capacity (depending on theLevel of Autonomy, L1-L5) of the vehicle controller of the electricvehicle is not sufficient to perform the computing tasks, declining toperform the computing tasks while the electric vehicle is electricallyconnected to the charging infrastructure in response to determining thatthe computing capacity of the vehicle controller of the electric vehicleis not sufficient to perform the computing tasks, and refraining fromperforming the computing tasks in response to declining to perform thecomputing tasks.

The present disclosure also describes an electric vehicle. In an aspectof the present disclosure, the electric vehicle includes a charge portconfigured to be electrically connected to a charging infrastructure anda controller in communication with the charge port. The controller isprogrammed to: advertise vehicle computing capabilities, and receivecomputing tasks while the electric vehicle is electrically connected toa charging infrastructure; accept to perform the computing tasks whilethe electric vehicle is electrically connected to the charginginfrastructure; and in response to accepting to perform the computingtasks, perform the computing tasks while the electric vehicle iselectrically connected to the charging infrastructure. The electricvehicle described in this paragraph improves vehicle technology andcomputer technology by using idle computing power available in electricvehicle for other applications, such as parallel, distributed, edge, andblockchain applications.

In an aspect of the present disclosure, the vehicle controller isprogrammed to: determine a computing capacity of a vehicle controller ofthe electric vehicle; determine whether the computing capacity of thevehicle controller of the electric vehicle is sufficient to perform thecomputing tasks; and accept to perform the computing tasks while theelectric vehicle is electrically connected to the charginginfrastructure in response to determining that the computing capacity ofthe vehicle controller of the electric vehicle is sufficient to performthe computing tasks.

In an aspect of the present disclosure, the vehicle controller isprogrammed to: receive a task rate for performing the computing tasks;receive a charging rate for charging the electric vehicle; determine anet profit using the charging rate for charging the electric vehicle andthe task rate for performing the computing tasks; compare the net profitwith a predetermined profit threshold to determine whether the netprofit is equal to or greater than the predetermined profit threshold;determine that the net profit is equal to or greater than thepredetermined profit threshold; accept to perform the computing taskswhile the electric vehicle is electrically connected to the charginginfrastructure in response to: (a) determining that the computingcapacity of the vehicle controller of the electric vehicle is sufficientto perform the computing tasks and (b) determining that the net profitis equal to or greater than the predetermined profit threshold; andperform the computing tasks in response to accepting to perform thecomputing tasks.

In an aspect of the present disclosure, the charging infrastructure is aselected charging infrastructure of a plurality of charginginfrastructures. The vehicle controller is programmed to: search for theplurality of charging infrastructures that are located within apredetermined distance from the electric vehicle; and receive the taskrate for performing the computing tasks for each of the plurality ofcharging infrastructures that are located within the predetermineddistance from the electric vehicle; receive the charging rate forcharging the electric vehicle for each of the plurality of charginginfrastructures that are located within the predetermined distance fromthe electric vehicle. The vehicle controller is further programmed to:determine the net profit for each of the plurality of charginginfrastructures that are located within the predetermined distance fromthe electric vehicle using the task rate for performing the computingtasks for each of the plurality of charging infrastructures that arelocated within the predetermined distance from the electric vehicle andthe charging rate for charging the electric vehicle for each of theplurality of charging infrastructures that are located within thepredetermined distance from the electric vehicle; and compare the netprofit for each of the plurality of charging infrastructures that arelocated within the predetermined distance from the electric vehicle witha predetermined profit threshold to determine whether the net profit isequal to or greater than the predetermined profit threshold to determinethe profitable charging infrastructures. The profitable charginginfrastructures are the plurality of charging infrastructures that arelocated within the predetermined distance from the electric vehicle andthat would result in the net profit that is equal to or greater than thepredetermined profit threshold. The vehicle controller is programmed toreceive a selection from a vehicle operator of one of the profitablecharging infrastructures.

In an aspect of the present disclosure, the vehicle controller isprogrammed to wirelessly receive the computing tasks from a remoteserver while the charging infrastructure is electrically charging theelectric vehicle through a charge port of the electric vehicle.

In an aspect of the present disclosure, the vehicle controller isprogrammed to receive the computing tasks from a remote server throughthe charging infrastructure. The electric vehicle is electricallyconnected to the charging infrastructure through a charge port of theelectric vehicle.

In an aspect of the present disclosure, the vehicle controller isprogrammed to use an idle computing power of a vehicle controller of theelectric vehicle to perform the computing tasks while the electricvehicle is electrically connected to the charging infrastructure througha charge port of the electric vehicle.

In an aspect of the present disclosure, the vehicle controller isprogrammed to perform the tasks at the same time as the charginginfrastructure is electrically charging the electric vehicle.

In an aspect of the present disclosure, the vehicle controller isfurther programmed to: receive a task rate for performing the computingtasks; receive a charging rate for charging the electric vehicle;determine a net profit using the charging rate for charging the electricvehicle and the task rate for performing the computing tasks; comparethe net profit with a predetermined profit threshold to determinewhether the net profit is less than the predetermined profit threshold;determine that the net profit is less than the predetermined profitthreshold; decline to perform the computing tasks while the electricvehicle is electrically connected to the charging infrastructure inresponse to determining that the net profit is less than thepredetermined profit threshold; and refrain from performing thecomputing tasks in response to declining to perform the computing tasks.

In an aspect of the present disclosure, the vehicle controller isfurther programmed to: determine a computing capacity of a vehiclecontroller of the electric vehicle; determine whether the computingcapacity of the vehicle controller of the electric vehicle is notsufficient to perform the computing tasks; decline to perform thecomputing tasks while the electric vehicle is electrically connected tothe charging infrastructure in response to determining that thecomputing capacity of the vehicle controller of the electric vehicle isnot sufficient to perform the computing tasks; and refrain fromperforming the computing tasks in response to declining to perform thecomputing tasks.

The above features and advantages, and other features and advantages, ofthe presently disclosed system and method are readily apparent from thedetailed description, including the claims, and exemplary embodimentswhen taken in connection with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure will become more fully understood from thedetailed description and the accompanying drawings, wherein:

FIG. 1 is a block diagram depicting an embodiment of an electricvehicle, which is part of a system for using idle computing power of anelectric vehicle;

FIG. 2 is a flowchart of a process for configuring the vehicleparameters, wherein this process is part of a method for using idlecomputing power of the electric vehicle of FIG. 1 ;

FIG. 3 is a flowchart of a method for using the electric vehicle as acomputing node;

FIG. 4 is a flowchart of a process for using the electric vehicle as acomputing node from a vehicle perspective, wherein this process is partof the method for using idle computing power of the electric vehicle ofFIG. 3 ;

FIG. 5 is a flowchart of a process for using the electric vehicle as acomputing node from the perspective of the charging infrastructure,wherein this process is part of the method for using idle computingpower of the electric vehicle of FIG. 3 ;

FIG. 6 is a flowchart of a process for using the electric vehicle as acomputing node from the perspective of the remote computing system,wherein this process is part of the method for using idle computingpower of the electric vehicle of FIG. 3 ;

FIG. 7A is part of a flowchart for a method for using the electricvehicle as a computing node according to an embodiment of the presentdisclosure; and

FIG. 7B is another part of the flowchart of FIG. 7A.

DETAILED DESCRIPTION

Reference will now be made in detail to several examples of thedisclosure that are illustrated in accompanying drawings. Wheneverpossible, the same or similar reference numerals are used in thedrawings and the description to refer to the same or like parts orsteps.

FIG. 1 schematically illustrates an electric vehicle 10, such as abattery electric vehicle (BEV) or a plug-in hybrid electric vehicle(PHEV). The electric vehicle 10 generally includes a chassis 12, a body14, front and rear wheels 17 and may be referred to as a vehicle system.In the depicted embodiment, the electric vehicle 10 includes two frontwheels 17 a and two rear wheels 17 b. The body 14 is arranged on thechassis 12 and substantially encloses components of the electric vehicle10. The body 14 and the chassis 12 may jointly form a frame. The wheels17 are each rotationally coupled to the chassis 12 near a respectivecorner of the body 14. The electric vehicle 10 includes a front axle 19coupled to the front wheels 17 a and a rear axle 25 coupled to the rearwheels 17 b.

In various embodiments, the electric vehicle 10 may be an autonomousvehicle and may be part of a system 98 for using idle computing power ofthe electric vehicle 10. The electric vehicle 10 is, for example, avehicle that is automatically controlled to carry passengers from onelocation to another. The electric vehicle 10 is depicted in theillustrated embodiment as a pickup truck, but it should be appreciatedthat other vehicles including, trucks, sedans, coupes, sport utilityvehicles (SUVs), recreational vehicles (RVs), etc., may also be used. Inan embodiment, the electric vehicle 10 may be a so-called a Level Two, aLevel Three, Level Four, or Level Five automation system. A Level Foursystem indicates “high automation,” referring to the drivingmode-specific performance by an automated driving system of aspects ofthe dynamic driving task, even if a human driver does not respondappropriately to a request to intervene. A Level Five system indicates“full automation,” referring to the full-time performance by anautomated driving system of aspects of the dynamic driving task under anumber of roadway and environmental conditions that can be managed by ahuman driver. In Level 3 vehicles, the vehicle systems perform theentire dynamic driving task (DDT) within the area that it is designed todo so. The vehicle operator is only expected to be responsible for theDDT-fallback when the electric vehicle 10 essentially “asks” the driverto take over if something goes wrong or the vehicle is about to leavethe zone where it is able to operate. In Level 2 vehicles, systemsprovide steering, brake/acceleration support, lane centering, andadaptive cruise control. However, even if these systems are activated,the vehicle operator at the wheel must be driving and constantlysupervising the automated features.

As shown, the electric vehicle 10 generally includes a propulsion system20, a steering system 24, a brake system 26, a sensor system 28, anactuator system 30, at least one data storage device 32, at least onevehicle controller 34, and a communication system 36. The propulsionsystem 20 may, in various embodiments, include an electric machine suchas a traction motor and/or a fuel cell propulsion system. The electricvehicle 10 may further include a battery (or battery pack) 21electrically connected to the propulsion system 20. Accordingly, thebattery 21 is configured to store electrical energy and to provideelectrical energy to the propulsion system 20. In certain embodiments,the propulsion system 20 may include an internal combustion engineand/or an electric motor. The electric vehicle 10 may include atransmission system 22 if the propulsion system 20 includes an internalcombustion engines. The transmission system 22 is configured to transmitpower from the propulsion system 20 to the vehicle wheels 17 accordingto selectable speed ratios. According to various embodiments, thetransmission system 22 may include a step-ratio automatic transmission,a continuously-variable transmission, or other appropriate transmission.The brake system 26 is configured to provide braking torque to thevehicle wheels 17. The brake system 26 may, in various embodiments,include friction brakes, brake by wire, a regenerative braking systemsuch as an electric machine, and/or other appropriate braking systems.The steering system 24 influences a position of the vehicle wheels 17and may include a steering wheel 33. While depicted as including asteering wheel 33 for illustrative purposes, in some embodimentscontemplated within the scope of the present disclosure, the steeringsystem 24 may not include a steering wheel 33.

The sensor system 28 includes one or more sensors 40 (i.e., sensingdevices) that sense observable conditions of the exterior environmentand/or the interior environment of the electric vehicle 10. The sensors40 are in communication with the vehicle controller 34 and may include,but are not limited to, one or more radars, one or more light detectionand ranging (lidar) sensors, one or more proximity sensors, one or moreodometers, one or more ground penetrating radar (GPR) sensors, one ormore steering angle sensors, one or more global positioning systems(GPS) transceivers 45, one or more tire pressure sensors, one or morecameras 41 (e.g., optical cameras and/or infrared cameras), one or moregyroscopes, one or more accelerometers, one or more inclinometers, oneor more speed sensors, one or more ultrasonic sensors, one or moreinertial measurement units (IMUs) and/or other sensors. Each sensor 40is configured to generate a signal that is indicative of the sensedobservable conditions of the exterior environment and/or the interiorenvironment of the electric vehicle 10. Because the sensor system 28provides data to the vehicle controller 34, the sensor system 28 and itssensors 40 are considered sources of information (or simply sources).

The sensor system 28 includes one or more Global Navigation SatelliteSystem (GNSS) transceivers 45 (e.g., Global Positioning System (GPS)transceivers) configured to detect and monitor the route data (i.e.,route information). The GNSS transceiver 45 is configured to communicatewith a GNSS to locate the position of the electric vehicle 10 in theglobe. The GNSS transceiver 45 is in electronic communication with thevehicle controller 34.

The actuator system 30 includes one or more actuator devices 42 thatcontrol one or more vehicle features such as, but not limited to, thepropulsion system 20, the transmission system 22, the steering system24, and the brake system 26. In various embodiments, the vehiclefeatures may further include interior and/or exterior vehicle featuressuch as, but are not limited to, doors, a trunk, and cabin features suchas air, music, lighting, etc.

The data storage device 32 stores data for use in automaticallycontrolling the electric vehicle 10. In various embodiments, the datastorage device 32 stores defined maps of the navigable environment. Invarious embodiments, the defined maps may be predefined by and obtainedfrom a remote system. For example, the defined maps may be assembled bythe remote system and communicated to the electric vehicle 10(wirelessly and/or in a wired manner) and stored in the data storagedevice 32. The data storage device 32 may be part of the vehiclecontroller 34, separate from the vehicle controller 34, or part of thevehicle controller 34 and part of a separate system.

The electric vehicle 10 may further include one or more airbags 35 incommunication with the vehicle controller 34 or another controller ofthe electric vehicle 10. The airbag 35 includes an inflatable bladderand is configured to transition between a stowed configuration and adeployed configuration to cushion the effects of an external forceapplied to the electric vehicle 10. The sensors 40 may include an airbagsensor, such as an IMU, configured to detect an external force andgenerate a signal indicative of the magnitude of such external force.The vehicle controller 34 is configured to command the airbag 35 todeploy based on the signal from one or more sensors 40, such as theairbag sensor. Accordingly, the vehicle controller 34 is configured todetermine when the airbag 35 has been deployed.

The vehicle controller 34 includes at least one vehicle processor 44 anda vehicle non-transitory computer readable storage device or media 46.The vehicle processor 44 may be a custom-made processor, a centralprocessing unit (CPU), a graphics processing unit (GPU), an auxiliaryprocessor among several processors associated with the vehiclecontroller 34, a semiconductor-based microprocessor (in the form of amicrochip or chip set), a macroprocessor, a combination thereof, orgenerally a device for executing instructions. The vehicle computerreadable storage device or media 46 may include volatile and nonvolatilestorage in read-only memory (ROM), random-access memory (RAM), andkeep-alive memory (KAM), for example. KAM is a persistent ornon-volatile memory that may be used to store various operatingvariables while the vehicle processor 44 is powered down. The vehiclecomputer-readable storage device or media 46 may be implemented using anumber of memory devices such as PROMs (programmable read-only memory),EPROMs (electrically PROM), EEPROMs (electrically erasable PROM), cloudstorage, flash memory, or another electric, magnetic, optical, orcombination memory devices capable of storing data, some of whichrepresent executable instructions, used by the vehicle controller 34 incontrolling the electric vehicle 10. The vehicle controller 34 of theelectric vehicle 10 may be programmed to execute at least part of themethods described in detail below.

The instructions may include one or more separate programs, each ofwhich comprises an ordered listing of executable instructions forimplementing logical functions. The instructions, when executed by thevehicle processor 44, receive and process signals from the sensor system28, perform logic, calculations, methods and/or algorithms forautomatically controlling the components of the electric vehicle 10, andgenerate control signals to the actuator system 30 to automaticallycontrol the components of the electric vehicle 10 based on the logic,calculations, methods, and/or algorithms. Although a single vehiclecontroller 34 is shown in FIG. 1 , embodiments of the electric vehicle10 may include a plurality of vehicle controllers 34 that communicateover a suitable communication medium or a combination of communicationmediums and that cooperate to process the sensor signals, perform logic,calculations, methods, and/or algorithms, and generate control signalsto automatically control features of the electric vehicle 10.

In various embodiments, one or more instructions of the vehiclecontroller 34 are embodied in the control system 98. The electricvehicle 10 includes a user interface 23, which may be a touchscreen inthe dashboard. The user interface 23 may include, but is not limited to,an alarm, such as one or more speakers 27 to provide an audible sound,haptic feedback in a vehicle seat or other object, one or more displays29, one or more microphones 31 and/or other devices suitable to providea notification to the vehicle user of the electric vehicle 10. The userinterface 23 is in electronic communication with the vehicle controller34 and is configured to receive inputs by a user (e.g., a vehicleoperator or a vehicle passenger). For example, the user interface 23 mayinclude a touch screen and/or buttons configured to receive inputs froma vehicle user 11 (FIG. 6 ). Accordingly, the vehicle controller 34 isconfigured to receive inputs from the user via the user interface 23.The vehicle controller 34 may also receive speech/voice inputs,gestures, and other similar input methods.

The electric vehicle 10 may include one or more displays 29 configuredto display information to the user (e.g., vehicle operator orpassenger). In certain embodiments, the display 29 may be configured asa head-up display (HUD), and/or an information cluster display. Theelectric vehicle 10 may additionally include GPU, a security module andone or more connectivity modules.

The software in the electric vehicle 10 may include an operating systemand locations services, network connectivity services, power monitor andcontrol, user profiles, charge profiles, and vehicle safety modules. Thesoftware in the electric vehicle 10 may include a client computeapplication (CCA) that checks user preferences for cost thresholds, timeduration restrictions (both schedule and artificial intelligence ormachine learning based), time of day charge (TODC) restrictions,locations, network bandwidth, and other restrictions to confirm if anincoming task can be processed. The software in the electric vehicle 10includes a billing module within CCA that negotiates with the remoteserver 50 for various job sizes based on parameters like availablecompute power, memory, battery state of charge, available (or projected)idle time, etc. The CCA prioritizes tasks for scheduling based on userpreferences and cost basis. Billing is handled by the billing module,and the billing module communicates with the remote server 50 for costand payment solutions. The software of the electric vehicle furtherincludes a compute client module (CCM) that authenticates with theremote server 50 and fetches tasks or work units. A work unit is asingle job/task that can be scheduled and completed independently by asingle CCA. The software of the electric vehicle 10 also includes anauthenticator module that verifies that the account, billing, and tasktransactions are following security measures. Further, the software ofthe electric vehicle 10 includes a vehicle safety module that ensurestasks are processed only when conditions are met and the electricvehicle 10 is connected to a charge port 39 before high performancecomputations are processed.

The communication system 36 is in communication with the vehiclecontroller 34 and is configured to wirelessly communicate information toand from a remote computing system 48, such as a cloud computing systemand/or a grid computing system. In certain embodiments, thecommunication system 36 is a wireless communication system configured tocommunicate via a wireless local area network (WLAN) using IEEE 802.11standards or by using cellular data communication. However, additionalor alternate communication methods, such as a dedicated short-rangecommunications (DSRC) channel, are also considered within the scope ofthe present disclosure. DSRC channels refer to one-way or two-wayshort-range to medium-range wireless communication channels specificallydesigned for automotive use and a corresponding set of protocols andstandards. Accordingly, the communication system 36 may include one ormore antennas and/or vehicle transceivers 37 for receiving and/ortransmitting signals. The vehicle transceivers 37 may be consideredsensors 40 or sources of information. The communication system 36 isconfigured to wirelessly communicate information between the electricvehicle 10 and another vehicle. Further, the communication system 36 isconfigured to wirelessly communicate information between the electricvehicle 10 and infrastructure or other vehicles.

The electric vehicle 10 further includes a charging port 39 that allowsthe electric vehicle 10 to be electrically connected to the receiveelectrical power from a charging infrastructure 58, such as a chargingstation. In the present disclosure, the term “charging infrastructure”is a piece of equipment that supplies electrical power for chargingplug-in electric vehicles 10. The charging port 39 is electricallyconnected to the battery (or battery pack) 21 of the electric vehicle10. Accordingly, when the electric vehicle 10 is electrically connectedto the charging infrastructure 58, the charging infrastructure 58 mayelectrically charge the battery (or battery pack) 21 through thecharging port 39 of the electric vehicle 10. The charging port 39 isalso in communication with the vehicle controller 34. As such, thevehicle controller 34 may send and receive signals from the charginginfrastructure 58 through the charging port 39.

The system 98 for using idle computing power of the electric vehicle 10includes a remote computing system 48, such as a cloud computing systemor a grid computing system. The remote computing system may be part ofthe charging infrastructure 58. The remote computing system 48 includesone or more remote servers 50 that are not physically connected to theelectric vehicle 10. Irrespective of the number of remote servers 50,each remote server 50 has a server controller 51 having at least oneserver processor 52 and at least one server non-transitory computerreadable storage device or media 54. The server processor 52 may be acustom-made processor, a central processing unit (CPU), a graphicsprocessing unit (GPU), an auxiliary processor among several processorsassociated with the server controller 51, a semiconductor-basedmicroprocessor (in the form of a microchip or chip set), amacroprocessor, a combination thereof, or generally a device forexecuting instructions. The server computer readable storage device ormedia 46 may include volatile and nonvolatile storage in read-onlymemory (ROM), random-access memory (RAM), and keep-alive memory (KAM),for example. KAM is a persistent or non-volatile memory that may be usedto store various operating variables while the server processor 44 ispowered down. The server computer-readable storage device or media 46may be implemented using a number of memory devices such as PROMs(programmable read-only memory), EPROMs (electrically PROM), EEPROMs(electrically erasable PROM), flash memory, or another electric,magnetic, optical, or combination memory devices capable of storingdata, some of which represent executable instructions. The servercontroller 51 of the electric vehicle 10 may be programmed to execute atleast part of the methods described in detail below. The remotecomputing system 48 may include one or more antennas and/or servertransceivers 56 for wirelessly receiving and/or transmitting signals.The server transceivers 56 enable the remote computing system 48 towirelessly communicate information between the electric vehicle 10 andthe remote computing system 48 or another entity. The electric vehicle10 and the remote computing system 48 may also physically/electricallycommunication with each other. The electric vehicle 10 also has theability to advertise its computing capabilities and capacity in additionto the ability to receive computing tasks.

The system 98 for using idle computing power of the electric vehicle 10includes a charging infrastructure 58 configured to supply electricalpower to the electric vehicle 10. The charging infrastructure 58includes a charging plug 60 configured, shaped, and sized to bephysically and electrically connected to the charging port 39 of theelectric vehicle 10. Thus, the charging plug 60 facilitates anelectrical connection between the electric vehicle 10 and the charginginfrastructure 58. In addition, the charging plug 60 facilitates signalcommunication between the vehicle controller 34 and the charginginfrastructure 58. The charging infrastructure 58 may be a chargingstation and includes a station controller 61 in communication with thevehicle controller 34 when the charging infrastructure 58 iselectrically connected to the electric vehicle 10. The stationcontroller 61 includes at least one station processor 62 and at leastone station non-transitory computer readable storage device or media 64.The station processor 62 may be a custom-made processor, a centralprocessing unit (CPU), a graphics processing unit (GPU), an auxiliaryprocessor among several processors associated with the server controller51, a semiconductor-based microprocessor (in the form of a microchip orchip set), a macroprocessor, a combination thereof, or generally adevice for executing instructions. The station computer readable storagedevice or media 64 may include volatile and nonvolatile storage inread-only memory (ROM), random-access memory (RAM), and keep-alivememory (KAM), for example. KAM is a persistent or non-volatile memorythat may be used to store various operating variables while the stationprocessor 62 is powered down. The station computer-readable storagedevice or media 64 may be implemented using a number of memory devicessuch as PROMs (programmable read-only memory), EPROMs (electricallyPROM), EEPROMs (electrically erasable PROM), flash memory, or anotherelectric, magnetic, optical, or combination memory devices capable ofstoring data, some of which represent executable instructions. Thestation controller 61 may be programmed to execute at least part of themethods described in detail below. The charging infrastructure 58 mayinclude one or more antennas and/or station transceivers 66 forwirelessly receiving and/or transmitting signals to and from theelectric vehicle 10 and/or the remote computing system 48. Therefore,the station transceivers 66 enable the charging infrastructure 58 towirelessly communicate information between the charging infrastructure58 and the remote computing system 48 and/or another entity.

The system 98 for using idle computing power of the electric vehicle 10may include a mobile device 68, such as a smartphone or a mobile tablet.The mobile device 68 includes one or more device controllers 69 forcontroller the operation of the mobile device 68. The device controller69 includes at least one device processor 70 and at least one devicenon-transitory computer readable storage device or media 72. The deviceprocessor 70 may be a custom-made processor, a central processing unit(CPU), a graphics processing unit (GPU), an auxiliary processor amongseveral processors associated with the device controller 69, asemiconductor-based microprocessor (in the form of a microchip or chipset), a macroprocessor, a combination thereof, or generally a device forexecuting instructions. The device computer readable storage device ormedia 72 may include volatile and nonvolatile storage in read-onlymemory (ROM), random-access memory (RAM), and keep-alive memory (KAM),for example. KAM is a persistent or non-volatile memory that may be usedto store various operating variables while the station processor 62 ispowered down. The station computer-readable storage device or media 64may be implemented using a number of memory devices such as PROMs(programmable read-only memory), EPROMs (electrically PROM), EEPROMs(electrically erasable PROM), flash memory, or another electric,magnetic, optical, or combination memory devices capable of storingdata, some of which represent executable instructions. The devicecontroller 69 may be programmed to execute at least part of the methodsdescribed in detail below. The mobile device 68 may include one or moreantennas and/or device transceivers 74 for wirelessly receiving and/ortransmitting signals to and from the electric vehicle 10, the charginginfrastructure 58, and/or the remote computing system 48. Therefore, thedevice transceivers 74 enable the mobile device 68 to wirelesslycommunicate information between the charging infrastructure 58 and theremote computing system 48 and/or the electric vehicle 10.

FIG. 2 is a flowchart of a process 100 for configuring vehicleparameters of the electric vehicle 10. The process 100 is part of amethod for using idle computing power of the electric vehicle 10. Theprocess 100 begins at block 102 and may be referred to as a userpre-configuration process. Then, the process 100 proceeds to block 104.At block 104, the vehicle operator opens an electric vehicle (EV)configuration user-interface screen in the user interface 23 of theelectric vehicle 10 or a mobile app in the mobile device 68 or desktopapp (e.g., web app). To do so, the vehicle controller 34 commands theuser interface 23 of the electric vehicle 10 to open the EVconfiguration screen in response to receiving an input from the vehicleoperator. Alternatively, the device controller 69 commands the mobiledevice 68 to open the EV configuration screen in response to receivingan input from the vehicle operator. Next, the process 100 proceeds toblock 106.

At block 106, the vehicle operator configures the external/commercialparameters through the user interface 23 of the electric vehicle 10and/or the mobile device 68. The external/commercial parameters are usedfor charging infrastructures 58 that are external to the vehicleoperator's home. As non-limiting examples, the vehicle operator mayinput and/or configure the desired net profit (e.g., predeterminedprofit threshold), the available charge time per session (which may bepre-populated from the vehicle profile), and the types of task packetsthat the electric vehicle 10 supports and the vehicle operator iswilling to accept for computations. Then, the process 100 proceeds toblock 108.

At block 108, the vehicle operator configures the home profileparameters through the user interface 23 of the electric vehicle 10and/or the mobile device 68. The home profile parameters are used forcharging infrastructures 58 at the vehicle operator's home. Asnon-limiting examples, the vehicle operator may input and/or configurethe desired net profit (e.g., predetermined profit threshold), theavailable charge time per session, and the types of task packets thatthe electric vehicle 10 supports and the vehicle operator is willing toaccept for computations. Then, the process 100 proceeds to block 110. Atblock 110, the home profile parameters and the (as configured by thevehicle operator) are saved and the external/commercial parameters ondata storage device 32 of the electric vehicle 10 and/or the serverstorage media 54 of the remote computing system 48. Then, the process100 continues to block 112. At block 112, the process 100 ends.

FIG. 3 is a method 200 for using the electric vehicle 10 as a computingnode in distributed, parallel, edge computing and/or blockchainoperations. The method 200 begins at block 202. Then, the method 200continues to block 204. At block 204, the electric vehicle 10 is parked,charging, and ready to compute. In other words, at block 204, thevehicle controller 34 determines that the electric vehicle 10 is parkedbased, for example, on the inputs from other components of the electricvehicle 10, such as the sensors 40. Also, at block 204, the vehiclecontroller 34 determines that the electric vehicle 10 is electricallyconnected to charging infrastructure 58 and the charging infrastructure58 currently supplying electrical power to the electric vehicle 10 basedon inputs from other components of the electric vehicle 10, such as thecharging port 39. Also, at block 204, the vehicle controller 34determines that it has idle computing power and is therefore ready tomake additional computations. Then, the method 200 proceeds to block206.

At block 206, the vehicle controller 34 of the electric vehicle 10communicates with the remote computing system 48 for authenticationpurposes. For example, the vehicle operator may input authenticationcredentials (e.g., username and password) and such authenticationcredentials are sent to the remote computing system 48. Then, the remotecomputing system 48 receives the authentication credentials from thevehicle controller 34. Then, the method 200 proceeds to block 208. Atblock 208, the remote computing system 48 grants the vehicle controller34 access to the remote computing system 48 if the authenticationcredentials match the authentication credentials stored in the remotecomputing system 48. If the authentication credentials sent by thevehicle controller 34 do not match the authentication credentials storedin the remote computing system 48, then the method 200 returns to block202. If the authentication credentials sent by the vehicle controller 34match the authentication credentials stored in the remote computingsystem 48, then method 200 proceeds to block 210.

At block 210, the vehicle controller 34 determines its computingcapacity. In the present disclosure, the term “computing capacity” meansthe transaction processing capability of a computer or a computersystem. According, the computing capacity of the vehicle controller 34is a transaction processing capacity of the vehicle controller 34. Then,the vehicle controller 34 communicates its computing capacity to theremote computing system 48. Next, the method 200 continues to block 212.

At block 212, the vehicle controller 34 waits and eventually receivesone or more computing tasks (i.e., task packets) from one or more remoteserver 50 of the remote computing system 48 as well as the rates forperforming one or more of the computing tasks. In the presentdisclosure, the term “computing task” means a unit of computing work.Therefore, at block 212, the remote computing system 48 sends one ormore tasks (i.e., task packets) to the vehicle controller 34. Thevehicle controller 34 may receive the computing tasks from the remoteserver 50 at the same time as the electric vehicle 10 is electricallyconnected to the charging infrastructure charging infrastructure 58. Inother words, the vehicle controller 34 receives the computing tasks atthe same time as the charging infrastructure 58 is supplying electricalpower to the electric vehicle 10. Then, the method 200 continues toblock 214.

At block 214, the vehicle controller 34 of the electric vehicle 10determines whether to accept or decline to perform the computing taskswhile the electric vehicle 10 is electrically connected to the charginginfrastructure 58. In other words, the vehicle controller 34 determineswhether to accept or decline to accept to perform the computing tasksreceived from the remote server 50 at the same time as the charginginfrastructure 58 is supplying electrical power to the electric vehicle10.

To determine whether to accept to perform the computing tasks, thevehicle controller 34 may take into account different considerationsdepending on whether the charging infrastructure 58 is a commercial siteor a home site. For commercial sites, the vehicle controller 34 mayconsider the net profit, the TODC rates, bidding considerations, chargeduration or how long the electric vehicle 10 is available (i.e.,guarantee compute time), the charge station availability (guaranteedfacility time), and/or other amenities, perks and discounts at thecommercial site. For home sites, the vehicle controller 34 may considerthe TODC rates (i.e., electricity rates at home) and/or the chargeduration or how long the electric vehicle 10 is available (i.e., theguaranteed compute time).

At block 214, the vehicle controller 34 determines whether its computingcapacity is sufficient to perform one or more of the computing tasksreceived from the remote computing system 48 (i.e., one or more remoteservers 50). The computing tasks may include, but are not limited to,blockchain transactions, solving complex scientific problems,computation and/or data storage closer to a specific location to improveresponse time, and/or hosting a virtual machine to handle the vehicleoperator's day-to-day tasks. If the computing capacity is not sufficientto perform one or more of the computing tasks, then the vehiclecontroller 34 declines to perform one or more computing tasks and themethod 200 continues to block 216. At block 216, the vehicle controller34 reports an error to the remote computing system 48 and refrains fromperforming the computing tasks. The computing tasks from variousinfrastructure companies may be queued. If the vehicle controller 34determines that its computing capacity is sufficient to perform one ormore computing tasks received from the remote computing system 48, thenthe vehicle controller 34 accepts to perform the computing tasks and themethod 200 may continue to block 218 depending on other considerations.Regarding these other considerations, the vehicle controller 34 maydetermine whether the rates for performing the computing tasks and therates for charging the electric vehicle 10, both of which may bereceived from the remote computing system 48 and/or the charginginfrastructure 58. The rates for performing the computing tasks may bereferred to as task rates, whereas the rates for charging the electricvehicle 10 may be referred to as charge rates. For instance, at block214, the vehicle controller 34 may determines (e.g., calculates) the netprofit for performing the computing task while electrically charging theelectric vehicle 10. To do so, the vehicle controller 34 considers therates for performing the computing tasks and the rates for electricallycharging the electric vehicle 10. For example, the net profit may bedetermined using the following equations;

Cost_(Overhead)=(C _(devSetup) +C _(Infra)+(C _(elec) ×T_(oDC)/(60*60))); and

NetProfit_((per session,per sec))=(Revenue_(EdevEarnPot)−Cost_(Overhead))

-   -   where    -   C_(elec) is the electricity cost in kilowatts per hour;    -   ToDC stands for Time Of Day Charge and is the electricity rate        based peak and non-peak rates;    -   C_(devSetup) is a device setup fee;    -   C_(Infra) is an infrastructure fee per second (or charging        infrastructure fee per second);    -   Cost_(overhead) is the cost of charging the electric vehicle 10        per second;    -   Revenue_(EdevEarnPot) is the revenue for computing the tasks        received from the received from the remote computing system 48        per second;    -   Net Profit_((per session, per sec)) is the net profit for        computing the tasks per session per second.

After determining the net profit, the vehicle controller 34 comparespreviously determined net profit with a predetermined profit thresholdto determine whether the net profit is greater than a profit threshold.Accordingly, the vehicle controller 34 determines whether the net profitis greater than the predetermined profit threshold. If the net profit isless than the predetermined profit threshold or computing capacity ofthe vehicle controller 34 is not sufficient to perform one or more ofthe computing tasks received from the remote computing system 48, thenthe method 200 continues to block 216. At block 216, the vehiclecontroller 34 reports an error to the remote computing system 48 andrefrains from performing the computing tasks received from the remoteserver 50. If the net profit is equal to or greater than thepredetermined profit threshold and the computing capacity of the vehiclecontroller 34 is sufficient to perform one or more computing tasksreceived from the remote computing system 48, then the vehiclecontroller 34 accepts to perform the computing tasks by sending anacceptance signal to the remote computing systems 48 and the method 200continues to block 218. The acceptance signal is indicative that thevehicle controller 34 accepted to perform one or more of the computingtasks received from the remote server 50. Upon receiving the acceptancesignal, the station controller 61 commands the charging infrastructure58 to electrically charge (i.e., supply electrical power) to theelectric vehicle 10. In response to this command, the charginginfrastructure 58 supplies electrical power to the electric vehicle 10.The charging may happen independent of the computations or regardless ofwhether computing tasks are being performed.

At block 218, the vehicle controller 34 uses its computing power toperform some or all computing tasks received from the remote computingsystems 48. Then, the method 200 proceeds to block 220. At block 220,the vehicle controller 34 sends the results of the computing tasks tothe remote computing systems 48. Next, the method 200 continues to block222. At block 222, the vehicle controller 34 determines whether theremore computing tasks to perform. If there are more computing tasks toperform, the method 200 returns to block 210. If all computing taskshave been performed, then the method 200 continues to block 224. Atblock 224, the vehicle controller 34 notifies the remote computingsystems 48 either that there has been an error or that the method 200has reached the end of the cycle. Then, the method 200 continues toblock 226. At block 226, the method 200 stops and ends.

FIG. 4 is a flowchart of a process 300 for using the electric vehicle asa computing node from a vehicle perspective. The process 300 is part ofthe method 200 and starts at block 302. At block 302, the vehiclecontroller 34 determines whether a vehicle operator is driving theelectric vehicle 10 based on one or more inputs from the sensors 40.Then, the process 300 continues to block 402. At block 402, the vehiclecontroller 34 determines whether the electric vehicle 10 the battery (orbattery pack) 21 of the electric vehicle 10 needs to be charged based onthe state of charge (SOC) of the battery pack 21. Alternatively, thevehicle controller 34 determines whether the vehicle operator would liketo take a break based on inputs from the vehicle operator. Next, theprocess 300 proceeds to block 304.

At block 304, in response to determining that the battery (or batterypack) 21 of the electric vehicle 10 needs to be charged or that thevehicle operator would like to take a break, the vehicle controller 34searches for charging infrastructures 58 within a predetermined distance(e.g., two miles) from the electric vehicle 10 or predetermined placeusing, for example, inputs from the (GPS) transceivers 45. In response,the vehicle controller 34 commands the user interface 23 of the electricvehicle 10 and/or the mobile device 68 (via the CCA) to display a listof the charging infrastructures 58 that are located within thepredetermined distance from the electric vehicle 10. The vehiclecontroller 34 may also (or alternatively) command the speakers 27 of theelectric vehicle 10 to utter a list of the list of the charginginfrastructures 58 that are located within the predetermined distancefrom the electric vehicle 10. The process 300 then proceeds to block308.

At block 308, the vehicle controller 34 receives the task rate forperforming the computing tasks for each of the plurality of charginginfrastructures 58 that are located within the predetermined distancefrom the electric vehicle 10. The vehicle controller 34 also receivesthe charging rate for charging the electric vehicle 10 for each of theplurality of charging infrastructures 58 that are located within thepredetermined distance from the electric vehicle 10. The vehiclecontroller 34 then determines the net profit for each of the pluralityof charging infrastructures 58 that are located within the predetermineddistance from the electric vehicle 10 using the task rate for performingthe computing tasks for each of the plurality of charginginfrastructures 58 that are located within the predetermined distancefrom the electric vehicle 10 and the charging rate for charging theelectric vehicle 10 for each of the plurality of charginginfrastructures 58 that are located within the predetermined distancefrom the electric vehicle 10. Also, at block 308, the vehicle controller34 compares the net profit for each of the plurality of charginginfrastructures 58 that are located within the predetermined distancefrom the electric vehicle 10 with a predetermined profit threshold todetermine whether the net profit for each of the plurality of charginginfrastructures 58 that are located within the predetermined distancefrom the electric vehicle 10 is equal to or greater than thepredetermined profit threshold to determine the profitable charginginfrastructures. The profitable charging infrastructures 58 are thecharging infrastructures 58 that are located within the predetermineddistance from the electric vehicle 10 and have a net profit is equal toor greater than the predetermined profit threshold. At block 308, thevehicle controller 34 also determines whether the charginginfrastructures 58 complies with any other criteria preconfigured by thevehicle operator. For example, the vehicle controller 34 may determinewhether its computing capacity is sufficient to perform the computingtasks required by the profitable charging infrastructures 58. Afterdetermining the profitable charging infrastructures 58, the process 300continues to block 310.

At block 310, the vehicle controller 34 commands the user interface 23and/or the mobile device 68 to display a list of the profitable charginginfrastructures 58 that match the criteria preconfigured by the vehicleoperator. In response to receiving the command from the vehiclecontroller 34, the user interface 23 and/or the mobile device 68 mayalso display the charging rates and the task rates for each of theprofitable charging infrastructures 58. The user interface 223 may alsohave criteria to filter and/or sort lists based on user commands. Theprocess 300 may then continue to block 312.

At block 312, the vehicle operator selects one of the profitablecharging infrastructures 58 (i.e., the selected charging infrastructure)using the user interface 23 and/or the mobile device 68. Accordingly,the vehicle controller 34 receives the selection made by the vehicleoperator of one of the profitable charging infrastructures 58. Theprocess 300 then proceeds to block 314.

At block 314, the remote server 50 of the remote computing system 48negotiates (e.g., sends) the vehicle controller 34 the task rates andthe charging rates for the selected charging infrastructure along withparking slot preferences for the selected charging infrastructure 58.Then, the process 300 proceeds to block 316.

At block 316, the vehicle operator or the vehicle controller 34 acceptsor declines the offer (including the charging rates and the task rates)from the selected charging infrastructure 58. If the vehicle operator orthe vehicle controller 34 declines the offer from the selected charginginfrastructure, then the process 300 continues to block 318. At block318, the vehicle controller 34 displays an error and then the process300 returns to block 310. If the vehicle operator or the vehiclecontroller 34 accepts the offer from the selected charginginfrastructure 58, then the process 300 proceeds to block 320.

At block 320, the selected charging infrastructure 58 electricallycharges the electric vehicle 10 at the same time that the vehiclecontroller 34 performs the computing tasks received from the remoteserver 50 of the remote computing system 48. The vehicle controller 34may receive the computing tasks through the charging plug 60 of theselected charging infrastructure 58 and/or wirelessly from the remoteserver 50 of the remote computing system 48 while the electric vehicle10 is electrically connected to the selected charging infrastructure 58.At block 318, the vehicle controller 34 may also report the results ofperforming the computing tasks to the remote server 50 of the remotecomputing system 48.

FIG. 5 is a flowchart of a process 400 for using the electric vehicle asa computing node from the perspective of the charging infrastructure.The process 400 begins at block 402. At block 402, the stationcontroller 61 determines whether the charging infrastructure 58 is readyto electrically charge the electric vehicle 10. Then, the process 400continues to block 404. At block 404, the station controller 61 connectsto the remote computing system 48 using the station transceivers 66 andreceives the computing tasks as well as the tasks rates for performingthe computing tasks from one or more remote servers 50. Then, theprocess 400 continues to block 406.

At block 406, the station controller 61 sends (i.e., communicates) thetasks rates for performing the computing tasks and the charge rates forcharging the electric vehicle 10 to one or more electric vehicle 10.Next, the process 400 proceeds to block 408.

At block 408, the station controller 61 sends one or more advertisementsto the vehicle controller 34. The advertisements include, but are notlimited, discount, promotions, and seasonal adjustments to the chargerates for charging the electric vehicle 10. For example, theadvertisement may be discount for charging the electric vehicle 10 inexchange for performing the computing tasks received from the remotecomputing system 48.

FIG. 6 is a flowchart of a process 500 for using the electric vehicle asa computing node from the perspective of the remote computing system 48.The process 500 begins at block 502. At block 502, the server controller51 of the remote server 50 determines whether the remote computingsystem 48 is ready. In response to the determining that the remotecomputing system 48 is ready, the process 500 continues to block 504.

At block 504, one or more remote servers 50 creates task packets, ascheduler, an authenticator, and billing processes. The track packetsare a list of computing tasks that should be performed. The schedulerschedules the order and/or time that the computing tasks should beperformed. The authenticator allows a vehicle operator to access theremote computing system 48 using authentication credentials. The billingprocesses allow the remote computing system 48 to bill the vehicleoperator for charging the electric vehicle 10 taking into accountsdiscounts for performing the computing tasks. The process 500 thenproceeds to block 506.

At block 506, the remote computing systems 48 uses the servertransceivers 56 to send the tasks packets (including the computing tasksincluding their types) and the task rates for performing the computingtasks to the relevant stakeholders (e.g., vehicle controller 34 of theelectric vehicle 10, mobile device 68, and/or the station processor 62of the charging infrastructure 58). Then, the process 500 continues toblock 508. At block 508, the remote computing system 48 schedules theperformance of the computing tasks by the vehicle controller 34. Next,the process 500 continues to block 510.

At block 510, the remote computing system 48 receives the results of theperformance of the computing tasks by the vehicle controller 34 aftersending the task packets to the vehicle controller 34. As discussedabove, the vehicle controller 34 performs the computing tasks at thesame time as the charging infrastructure 58 electrically charges theelectric vehicle 10. Also, at block 510, the remote computing system 48validates the results of the performance of the computing tasks. Then,the process 500 continues to block 512.

At block 512, the remote computing system 48 updates the billing forelectrically charging the electric vehicle 10 based on the fact that thevehicle controller 34 performed the computing tasks. Thus, at block 512,the remote computing system 48 bills the vehicle operator of theelectric vehicle 10 for electrically charging the electric vehicle 10while providing a discount for using the idle computing power of thevehicle controller 34 to perform the computing tasks. The process 500then continues to block 514.

At block 514, the remote computing system 48 determines whether thecomputing tasks have been performed by the vehicle controller 34. Inresponse to the determining that the computing tasks have been performedby the vehicle controller 34, the remote computing system 48 flushes andpurges the computing tasks that have been performed by the vehiclecontroller 34.

FIG. 7 is a flowchart for a method 600 for using the electric vehicle 10as a computing node according to an embodiment of the presentdisclosure. The method 600 begins at block 602. Then, the method 600proceeds to block 604. At block 602, the vehicle controller 34determines whether the electric vehicle 10 is parked, is connected tothe charge plug 60 of the charging infrastructure 58 and has networkconnectivity. If the electric vehicle 10 is not parked, is not connectedto the charge plug 60 or does not have network connectivity, then themethod 600 returns to block 602. If the electric vehicle 10 is parked,is connected to the charge plug 60 of the charging infrastructure 58 andhas network connectivity, then method 600 continues to block 606.

Block 606 entails authenticating the electric vehicle 10 with thecharging infrastructure 58 and the remote computing system 48. If theauthentication is successful, the method 600 proceeds to block 608. Atblock 608, the vehicle controller 34 request the charging informationfrom the charging infrastructure 58. Then, the method 600 continues toblock 610. In response to this request, the charging infrastructure 58sends the charging information to the vehicle controller 34. Afterreceiving the charging information from the charging infrastructure 58,the method 600 continues to block 612.

At block 612, the vehicle controller 34 requests the computing taskinformation from the remote servers 50 of the remote computing system48. The computing task information includes contract terms forperforming the computing tasks. Upon receipt of the computing taskinformation from the remote servers 50, the method 600 continues toblock 614.

At block 614, the vehicle operator of the electric vehicle 10 accepts ordeclines the contract terms for performing the computing tasks or thevehicle controller 34 determines whether the contract terms match thepreset configuration thresholds. If the vehicle operator declines thecontract terms or the vehicle controller 34 determines that the contractterms do not match the present configuration threshold, then the method600 returns to block 610. If the vehicle operator accepts the contractterms or the contract terms match the preset configuration thresholds,then the method 600 continues to block 616. At block 616, the vehiclecontroller 34 negotiates the contract with the charging infrastructure58 and the remote computing system 48. Then, the method 600 continues toblock 618.

At block 618, the remote computing system 48 determines whether thecontract has been accepted. If the contract has not been accepted, themethod 600 returns to block 610. If the contract has been accepted, themethod 600 continues to block 620. At block 620, the vehicle controller34 requests one or more tasks from the remote computing system 48. Uponreceipt of the tasks by the vehicle controller 34, the method 600proceeds to block 622.

At block 622, the vehicle controller 34 processes one or more tasksreceived from the remote computing system 48. After the tasks have beencompleted, the method 600 proceeds to block 624. The vehicle controller34 sends the updated results of the computing tasks to the remotecomputing system 48. Then, the method 600 continues to block 626. Atblock 626, the remoting computing system 48 may accept or decline theresults of the performance of the computing tasks. If the remotecomputing system 48 declines the results, then the method 600 returns toblock 622 and the computing tasks may be retried. If the remotecomputing system 48 accepts the results, then the method 600 continuesto block 628. At block 628, the remote computing system 48 updates thebilling. After the billing has been updated, the method 600 continues toblock 630. At block 630, the remote computing system 48 determineswhether more computations are needed. If more computations are needed,then the method 600 returns to block 610. If no more computations areneeded, then the method 600 continues to block 632. At block 632, thecomputing tasks are purged. Then, the method 600 continues to block 634.At block 634, the method 600 ends.

While exemplary embodiments are described above, it is not intended thatthese embodiments describe all possible forms encompassed by the claims.The words used in the specification are words of description rather thanlimitation, and it is understood that various changes can be madewithout departing from the spirit and scope of the disclosure. Aspreviously described, the features of various embodiments can becombined to form further embodiments of the presently disclosed systemand method that may not be explicitly described or illustrated. Whilevarious embodiments could have been described as providing advantages orbeing preferred over other embodiments or prior art implementations withrespect to one or more desired characteristics, those of ordinary skillin the art recognize that one or more features or characteristics can becompromised to achieve desired overall system attributes, which dependon the specific application and implementation. These attributes caninclude, but are not limited to cost, strength, durability, life cyclecost, marketability, appearance, packaging, size, serviceability,weight, manufacturability, ease of assembly, etc. As such, embodimentsdescribed as less desirable than other embodiments or prior artimplementations with respect to one or more characteristics are notoutside the scope of the disclosure and can be desirable for particularapplications.

The drawings are in simplified form and are not to precise scale. Forpurposes of convenience and clarity only, directional terms such as top,bottom, left, right, up, over, above, below, beneath, rear, and front,may be used with respect to the drawings. These and similar directionalterms are not to be construed to limit the scope of the disclosure inany manner.

Embodiments of the present disclosure are described herein. It is to beunderstood, however, that the disclosed embodiments are merely examplesand other embodiments can take various and alternative forms. Thefigures are not necessarily to scale; some features could be exaggeratedor minimized to display details of particular components. Therefore,specific structural and functional details disclosed herein are not tobe interpreted as limiting, but merely as a representative basis forteaching one skilled in the art to variously employ the presentlydisclosed system and method. As those of ordinary skill in the art willunderstand, various features illustrated and described with reference toany one of the figures may be combined with features illustrated in oneor more other figures to produce embodiments that are not explicitlyillustrated or described. The combinations of features illustratedprovide representative embodiments for typical applications. Variouscombinations and modifications of the features consistent with theteachings of this disclosure, however, could be desired for particularapplications or implementations.

Embodiments of the present disclosure may be described herein in termsof functional and/or logical block components and various processingsteps. It should be appreciated that such block components may berealized by a number of hardware, software, and/or firmware componentsconfigured to perform the specified functions. For example, anembodiment of the present disclosure may employ various integratedcircuit components, e.g., memory elements, digital signal processingelements, logic elements, look-up tables, or the like, which may carryout a variety of functions under the control of one or moremicroprocessors or other control devices. In addition, those skilled inthe art will appreciate that embodiments of the present disclosure maybe practiced in conjunction with a number of systems, and that thesystems described herein are merely exemplary embodiments of the presentdisclosure.

For the sake of brevity, techniques related to signal processing, datafusion, signaling, control, and other functional aspects of the systems(and the individual operating components and communication protocols ofthe systems) may not be described in detail herein. Furthermore, theconnecting lines shown in the various figures contained herein areintended to represent example functional relationships and/or physicalcouplings between the various elements. It should be noted thatalternative or additional functional relationships or physicalconnections may be present in an embodiment of the present disclosure.

This description is merely illustrative in nature and is in no wayintended to limit the disclosure, its application, or uses. The broadteachings of the disclosure can be implemented in a variety of forms.Therefore, while this disclosure includes particular examples, the truescope of the disclosure should not be so limited since othermodifications will become apparent upon a study of the drawings, thespecification, and the following claims.

What is claimed is:
 1. A method for using idle computing power of anelectric vehicle, comprising: receiving computing tasks while theelectric vehicle is electrically connected to a charging infrastructure;accepting to perform the computing tasks while the electric vehicle iselectrically connected to the charging infrastructure; and in responseto accepting to perform the computing tasks, performing the computingtasks while the electric vehicle is electrically connected to thecharging infrastructure.
 2. The method of claim 1, further comprising:determining a computing capacity of a vehicle controller of the electricvehicle; and wherein accepting to perform the computing tasks while theelectric vehicle is electrically connected to the charginginfrastructure includes: determining whether the computing capacity ofthe vehicle controller of the electric vehicle is sufficient to performthe computing tasks; and accepting to perform the computing tasks whilethe electric vehicle is electrically connected to the charginginfrastructure in response to determining that the computing capacity ofthe vehicle controller of the electric vehicle is sufficient to performthe computing tasks.
 3. The method of claim 2, further comprising:receiving a task rate for performing the computing tasks; receiving acharging rate for charging the electric vehicle; determining a netprofit using the charging rate for charging the electric vehicle and thetask rate for performing the computing tasks; comparing the net profitwith a predetermined profit threshold to determine whether the netprofit is equal to or greater than the predetermined profit threshold;determining that the net profit is equal to or greater than thepredetermined profit threshold; and wherein accepting to perform thecomputing tasks while the electric vehicle is electrically connected tothe charging infrastructure includes: accepting to perform the computingtasks while the electric vehicle is electrically connected to thecharging infrastructure in response to: (a) determining that thecomputing capacity of the vehicle controller of the electric vehicle issufficient to perform the computing tasks and (b) determining that thenet profit is equal to or greater than the predetermined profitthreshold; and performing the computing tasks in response to acceptingto perform the computing tasks.
 4. The method of claim 3, wherein: thecharging infrastructure is a selected charging infrastructure of aplurality of charging infrastructures; searching for the plurality ofcharging infrastructures that are located within a predetermineddistance from the electric vehicle or a predetermined location;receiving the task rate for performing the computing tasks for each ofthe plurality of charging infrastructures that are located within thepredetermined distance from the electric vehicle; receiving the chargingrate for charging the electric vehicle for each of the plurality ofcharging infrastructures that are located within the predetermineddistance from the electric vehicle; determining the net profit for eachof the plurality of charging infrastructures that are located within thepredetermined distance from the electric vehicle using the task rate forperforming the computing tasks for each of the plurality of charginginfrastructures that are located within the predetermined distance fromthe electric vehicle and the charging rate for charging the electricvehicle for each of the plurality of charging infrastructures that arelocated within the predetermined distance from the electric vehicle;comparing the net profit for each of the plurality of charginginfrastructures that are located within the predetermined distance fromthe electric vehicle with a predetermined profit threshold to determinewhether the net profit is equal to or greater than the predeterminedprofit threshold to determine profitable charging infrastructures,wherein the profitable charging infrastructures are the plurality ofcharging infrastructures that are located within the predetermineddistance from the electric vehicle and that would result in the netprofit that is equal to or greater than the predetermined profitthreshold; and receiving a selection from a vehicle operator of one ofthe profitable charging infrastructures.
 5. The method of claim 1,wherein receiving the computing tasks while the electric vehicle iselectrically connected to the charging infrastructure includeswirelessly receiving the computing tasks from a remote server while thecharging infrastructure is electrically charging the electric vehiclethrough a charge port of the electric vehicle.
 6. The method of claim 1,wherein receiving the computing tasks while the electric vehicle iselectrically connected to the charging infrastructure includes receivingthe computing tasks from a remote server through the charginginfrastructure, and the electric vehicle is electrically connected tothe charging infrastructure through a charge port of the electricvehicle.
 7. The method of claim 1, wherein performing the computingtasks while the electric vehicle is electrically connected to thecharging infrastructure includes using an idle computing power of avehicle controller of the electric vehicle to perform the computingtasks while the electric vehicle is electrically connected to thecharging infrastructure through a charge port of the electric vehicle.8. The method of claim 7, wherein the vehicle controller performs thetasks at the same time as the charging infrastructure is electricallycharging the electric vehicle.
 9. The method of claim 1, furthercomprising: receiving a task rate for performing the computing tasks;receiving a charging rate for charging the electric vehicle; determininga net profit using the charging rate for charging the electric vehicleand the task rate for performing the computing tasks; comparing the netprofit with a predetermined profit threshold to determine whether thenet profit is less than the predetermined profit threshold; determiningthat the net profit is less than the predetermined profit threshold;declining to perform the computing tasks while the electric vehicle iselectrically connected to the charging infrastructure in response todetermining that the net profit is less than the predetermined profitthreshold; and refraining from performing the computing tasks inresponse to declining to perform the computing tasks.
 10. The method ofclaim 1, further comprising: determining a computing capacity of avehicle controller of the electric vehicle; determining whether thecomputing capacity of the vehicle controller of the electric vehicle isnot sufficient to perform the computing tasks; and declining to performthe computing tasks while the electric vehicle is electrically connectedto the charging infrastructure in response to determining that thecomputing capacity of the vehicle controller of the electric vehicle isnot sufficient to perform the computing tasks; and refraining fromperforming the computing tasks in response to declining to perform thecomputing tasks.
 11. An electric vehicle, comprising: a charge portconfigured to be electrically connected to a charging infrastructure; avehicle controller in communication with the charge port, wherein thevehicle controller is programmed to: receive computing tasks while theelectric vehicle is electrically connected to the charginginfrastructure; accept to perform the computing tasks while the electricvehicle is electrically connected to the charging infrastructure; and inresponse to accepting to perform the computing tasks, perform thecomputing tasks while the electric vehicle is electrically connected tothe charging infrastructure.
 12. The electric vehicle of claim 11,wherein the vehicle controller is programmed to: determine a computingcapacity of a vehicle controller of the electric vehicle; determinewhether the computing capacity of the vehicle controller of the electricvehicle is sufficient to perform the computing tasks; and accept toperform the computing tasks while the electric vehicle is electricallyconnected to the charging infrastructure in response to determining thatthe computing capacity of the vehicle controller of the electric vehicleis sufficient to perform the computing tasks.
 13. The electric vehicleof claim 12, wherein the vehicle controller is programmed to: receive atask rate for performing the computing tasks; receive a charging ratefor charging the electric vehicle; determine a net profit using thecharging rate for charging the electric vehicle and the task rate forperforming the computing tasks; compare the net profit with apredetermined profit threshold to determine whether the net profit isequal to or greater than the predetermined profit threshold; determinethat the net profit is equal to or greater than the predetermined profitthreshold; accept to perform the computing tasks while the electricvehicle is electrically connected to the charging infrastructure inresponse to: (a) determining that the computing capacity of the vehiclecontroller of the electric vehicle is sufficient to perform thecomputing tasks and (b) determining that the net profit is equal to orgreater than the predetermined profit threshold; and perform thecomputing tasks in response to accepting to perform the computing tasks.14. The electric vehicle of claim 13, wherein: the charginginfrastructure is a selected charging infrastructure of a plurality ofcharging infrastructures; wherein the vehicle controller is programmedto: search for the plurality of charging infrastructures that arelocated within a predetermined distance from the electric vehicle;receive the task rate for performing the computing tasks for each of theplurality of charging infrastructures that are located within thepredetermined distance from the electric vehicle; receive the chargingrate for charging the electric vehicle for each of the plurality ofcharging infrastructures that are located within the predetermineddistance from the electric vehicle; determine the net profit for each ofthe plurality of charging infrastructures that are located within thepredetermined distance from the electric vehicle using the task rate forperforming the computing tasks for each of the plurality of charginginfrastructures that are located within the predetermined distance fromthe electric vehicle and the charging rate for charging the electricvehicle for each of the plurality of charging infrastructures that arelocated within the predetermined distance from the electric vehicle;compare the net profit for each of the plurality of charginginfrastructures that are located within the predetermined distance fromthe electric vehicle with a predetermined profit threshold to determinewhether the net profit is equal to or greater than the predeterminedprofit threshold to determine the profitable charging infrastructures,wherein the profitable charging infrastructures are the plurality ofcharging infrastructures that are located within the predetermineddistance from the electric vehicle and that would result in the netprofit that is equal to or greater than the predetermined profitthreshold; and receive a selection from a vehicle operator of one of theprofitable charging infrastructures.
 15. The electric vehicle of claim11, wherein the vehicle controller is programmed to wirelessly receivethe computing tasks from a remote server while the charginginfrastructure is electrically charging the electric vehicle through thecharge port of the electric vehicle.
 16. The electric vehicle of claim11, wherein the vehicle controller is programmed to receive thecomputing tasks from a remote server through the charginginfrastructure, and the electric vehicle is electrically connected tothe charging infrastructure through the charge port of the electricvehicle.
 17. The electric vehicle of claim 11, wherein the vehiclecontroller is programmed to use an idle computing power of a vehiclecontroller of the electric vehicle to perform the computing tasks whilethe electric vehicle is electrically connected to the charginginfrastructure through the charge port of the electric vehicle.
 18. Theelectric vehicle of claim 17, wherein the vehicle controller isprogrammed to perform the tasks at the same time as the charginginfrastructure is electrically charging the electric vehicle.
 19. Theelectric vehicle of claim 11, wherein the vehicle controller is furtherprogrammed to: receive a task rate for performing the computing tasks;receive a charging rate for charging the electric vehicle; determine anet profit using the charging rate for charging the electric vehicle andthe task rate for performing the computing tasks; compare the net profitwith a predetermined profit threshold to determine whether the netprofit is less than the predetermined profit threshold; determine thatthe net profit is less than the predetermined profit threshold; declineto perform the computing tasks while the electric vehicle iselectrically connected to the charging infrastructure in response todetermining that the net profit is less than the predetermined profitthreshold; and refrain from performing the computing tasks in responseto declining to perform the computing tasks.
 20. The electric vehicle ofclaim 11, wherein the vehicle controller is further programmed to:determine a computing capacity of a vehicle controller of the electricvehicle; determine whether the computing capacity of the vehiclecontroller of the electric vehicle is not sufficient to perform thecomputing tasks; decline to perform the computing tasks while theelectric vehicle is electrically connected to the charginginfrastructure in response to determining that the computing capacity ofthe vehicle controller of the electric vehicle is not sufficient toperform the computing tasks; and refrain from performing the computingtasks in response to declining to perform the computing tasks.